Local Communications

This section describes communication between a protected application and the local Sentinel License Manager service.

A protected application communicates only with Sentinel License Manager on the computer where the application is running, regardless of whether the Sentinel HL or SL Key is located on the same computer or on a remote computer.

NOTE   Under Windows, Sentinel License Manager is a service that is launched automatically by hasplms.exe. Under Mac OS and Linux, the Sentinel License Manager is a process launched automatically by hasplmd.

Sentinel License Manager service opens socket 1947 for listening (both for UDP packets and TCP packets).

>IPv4 sockets are always opened (Sentinel License Manager currently does not work without IPv4 installed).

>IPv6 sockets are opened if IPv6 is available.

A protected application tries to connect to 127.0.0.1:1947 TCP to communicate with Sentinel License Manager. If an application uses multiple sessions, multiple concurrent TCP connections may exist. If a session is unused for a certain number of minutes (at least seven minutes, but the exact number depends on several factors), the session may be closed and automatically re-opened later in order to limit resources used by the application.

These local communications currently use IPv4 only.

The communication uses binary data blocks of varying size.